• The entire problem has been identified.
• Conflict Catcher will now try reordering startup files to see if the problem goes away.

• Conflict Catcher will now determine if the problem still exists, and restart your computer.

• Because the problem hasn't yet existed during the test, we must verify that it exists.
• Conflict Catcher will now activate the remaining suspect.

• Conflict Catcher will now determine if the problem really exists, and restart your computer.

• The next step is to see if the entire problem has been found.
• Conflict Catcher will now activate the files found to be part of the problem.

• Conflict Catcher will now determine if the problem still exists, and restart your computer.

• Because the problem existed, the suspects that were inactive have been ruled out.
• Conflict Catcher will now activate half of the remaining suspects.

• Conflict Catcher will now determine if the problem still exists, and restart your computer.

• Because the problem was gone, the suspects that were active have been ruled out.
• Conflict Catcher will now activate half of the remaining suspects.

• Conflict Catcher will now determine if the problem still exists, and restart your computer.

• Because the problem was gone, there must be a file conflict.
• Conflict Catcher will now activate half of the suspect files.

• Conflict Catcher will now determine if the problem still exists, and restart your computer.

• Because the problem was gone, there must be a file conflict.
• Conflict Catcher will now activate the files your intuition said contained the problem.

• Conflict Catcher will now determine if the problem still exists, and restart your computer.

• The next step is to see if the problem is actually being caused by a startup file.

• Conflict Catcher will now determine if the problem still exists, and restart your computer.

To interrupt the automatic process, click in the window.

• To begin the Conflict Test, you must restart the computer.